| Main Description |
Example 1:
The assignment to the test process covers the testing of all software (package and custom-made) that project
XYZ will deliver. The scope of this project is described in section x.x. The software must be tested to the extent that
a solid personnel administration with adequately converted data can be taken into production. The test process is split
up into the test levels described in section y.y and set up in such a way that any risks can be identified in a timely
manner. The aim is to issue a well-founded advice in relation to commissioning based on the insight into the quality of
the system to be delivered.
Example 2:
The master test plan represents a supplement to the project plan XYZ. This plan is used for e.g. project delimitation,
scope, planning, etc. The project’s aim is to render workplace support to BDE compliant. In simple terms, this can be
translated as:
-
Making XYZ suitable for running under Windows/XP
-
Organising access to workplace support via BDE.
The master test plan describes the relationship between test levels system test (ST), users acceptance test (UAT), and
production acceptance test (PAT). The test activities in these test levels must be aligned as optimally as possible.
This means that unnecessary, duplicate and/or non-testing of specific objects is prevented. The test strategy was
created in consultation with the XYZ project leader and line manager Test & Support. The relationship between the
test levels is described in general terms in the master test plan. The responsible party creates a separate detail test
plan for
each test level.
The overall test assignment is report whether, and if yes, which, risks incurs when taking XYZ release 2006 1.5
into production on the basis of the tests executed within the selected test strategy.
Example 3:
Use the project ‘Centralisation SYS-VS’ as a pilot to evaluate the proposed new test approach for the components as
defined in the scope. Remain within the framework of the PID (Project Initiation Document) until the integration and
explicitly exclude the overall project (SYS release 3.0) for this plan. The project has already been determined
planning-wise; the approach must be subject to this. Components in the plan can be applied if they add clear value to
the direct, ongoing activities and agreement has been reached, such at the discretion of the project leader.
Example 4:
In the first phase of Chain Automation, several quality management measures – including test and evaluation
activities – are organised. These activities must be executed in time and with insight into the desired quality on the
part of all stakeholders.
The plan describes the arrangements between the partners in terms of the tests and evaluations that are executed and
which parties are responsible. It is established what insights and reports will be delivered on the basis of which
decisions can be made.
|
